-
Notifications
You must be signed in to change notification settings - Fork 38.4k
Added configurable maxFramePayloadLength to ReactorNettyWebSocketClient #22367
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
...rc/main/java/org/springframework/web/reactive/socket/client/ReactorNettyWebSocketClient.java
Outdated
Show resolved
Hide resolved
…y, Added Javadocs
I noticed that this PR did not change It seems odd that the Is this intended? Will something bad happen if |
Good catch @philsttr, thanks. |
Is it possible to use this feature now or do we have to wait for the milestone? |
Currently the ReactorNettyWebSocketClient (RNWSC) doesn't allow for a configurable maxFramePayloadLength. The HttpClient used by the RNWSC allows for a configurable maxFramePayloadLength however, the method .websocket() used by the RNWSC ignores whatever is set by the HttpClient and uses a default value of 65536. As shown below:
ReactorNettyWebSocketClient invokes .websocket()
The method invoked on the HttpClient ignores the value you may have set in your HttpClient
I've solved the issue by using the overloaded .websocket() method on the HttpClient which takes a maxFramePayloadLength.
The maxFramePayloadLength is now configurable in the RNWSC.